feat(task): add scheduled starts, drag reorder, and preemptive queue cap - #123

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/renderer/components/TaskDetail/TaskGeneral.vue">

<violation number="1" location="src/renderer/components/TaskDetail/TaskGeneral.vue:257">
P2: Task detail now re-renders every second even for non-scheduled tasks because the timer is started unconditionally in `mounted`. Gating interval startup to valid future scheduled tasks avoids unnecessary UI churn and background work.</violation>
</file>

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/release.yml:
- Around line 354-360: The new Upload updater fragment step uses an unpinned
actions/upload-artifact@v4 reference, so update the release workflow to pin this
action to a specific commit SHA like the existing Swatinem/rust-cache usage.
Keep the step name and artifact settings in place, and only replace the action
reference in the upload-artifact step to match the repo’s supply-chain hardening
practice.
- Line 265: The release workflow still interpolates github.ref and matrix.target
directly inside run scripts, which static analysis flags as template-injection
risk. Update the affected shell/PowerShell steps to pass these values through
env in the job/step definition and then reference the environment variables
inside the scripts instead of using inline ${{ }} expressions. Apply this
pattern consistently in the release job call sites around the tag check and the
matrix-based commands so the existing workflow logic in release.yml remains
unchanged while reducing injection surface.
- Around line 506-542: The new updater-manifest job in release.yml uses several
third-party actions that are still referenced by version tags, so update the
actions used in the updater-manifest steps (checkout, setup-node,
download-artifact, and action-gh-release) to commit SHAs to match the project’s
pinned-action precedent. Also review the Setup Node.js step to confirm no
unintended caching is enabled by actions/setup-node, and only add an explicit
cache setting if it is intentionally required.
- Around line 333-352: The "Emit updater manifest fragment" step in the release
workflow builds JSON by manually printf’ing interpolated values for key, asset,
and signature, which is fragile if any value contains characters that need
escaping. Update this step to generate the fragment with a JSON-encoding tool or
method instead of hand-assembling the string, and keep the same inputs from the
matrix target, APP_ASSET, and UPDATER_SIG_FILE while preserving the existing
fragment file naming and output behavior.

In `@scripts/build-updater-manifest.mjs`:
- Line 27: The CLI entry-point check in the top-level `import.meta.url`
comparison is using a string path form that is not cross-platform. Update the
`build-updater-manifest.mjs` CLI detection to compare against
`pathToFileURL(process.argv[1]).href` instead of manually interpolating
`process.argv[1]`, so the entry-point check works correctly on Windows and other
platforms.

In `@src-tauri/risuko-engine/src/engine/manager.rs`:
- Around line 2621-2657: `set_task_schedule` has a race because it cancels the
active download before the task status is updated, which can let the
cancellation handler overwrite the intended `Scheduled` state. Update
`set_task_schedule` in `manager.rs` to follow the same ordering as `preempt()`:
first validate the task and set `task.status = TaskStatus::Scheduled` (and
related fields) under the write lock, then cancel any active download token
afterward. Keep the cancellation scoped to only the successful scheduling path
so it does not run before `kind`/`status` checks.

In `@src/renderer/components/Native/EngineClient.vue`:
- Around line 1048-1060: The checkMissedSchedules async path is swallowing fetch
errors, unlike the other handlers in EngineClient.vue that log failures. Update
the catch in checkMissedSchedules to record the rejection with logger.warn using
a clear message and the error object, while keeping the existing missed-task
handling logic unchanged; use the checkMissedSchedules, fetchScheduledTaskList,
and logger.warn symbols to locate the fix.

In `@src/renderer/components/Task/AddTask.vue`:
- Around line 207-215: The torrent submission flow is still inheriting the
shared form.startAt value, so update the AddTask.vue submission logic to clear
or omit the schedule field whenever type is torrent. Check the form handling
around the DateTimePicker and the payload builder for the task submission path,
and ensure the torrent case never includes risuko-start-at even when mixed tasks
were previously scheduled.

In `@src/renderer/components/Task/MissedScheduleDialog.vue`:
- Around line 101-122: The startNow/startAll flow in MissedScheduleDialog.vue is
swallowing start failures and then removing items from missedScheduledTasks
anyway. Update the startNow and startAll methods to handle errors like
ScheduleDialog.vue confirm() does by surfacing a message via
this.$msg?.error?.(...) and only removing a task from the missed list or closing
the dialog after a successful useTaskStore().startNow call; keep the
remaining-task refresh logic in startNow and the loop in startAll consistent
with that behavior.
- Around line 114-122: The startAll method in MissedScheduleDialog.vue is
dispatching missed tasks sequentially by awaiting each
useTaskStore().startNow(t.gid) call inside the loop, which makes N tasks incur N
round-trips. Update startAll to trigger all startNow calls concurrently, ideally
using Promise.allSettled over the pending list, and keep the close() call after
all dispatches complete; preserve or improve error handling so failures are not
silently swallowed.

In `@src/renderer/components/Task/ScheduleDialog.vue`:
- Around line 59-62: The ScheduleDialog task prop is loosely typed as a generic
Object, which drops the DownloadTask shape used by getTaskName, task.gid, and
task?.startAt. Update the props definition in ScheduleDialog.vue to use a
PropType for DownloadTask | null (with the same null default) so the component
stays type-safe and aligned with the rest of the task usage.

In `@src/renderer/components/Task/TaskItem.vue`:
- Around line 5-20: The TaskItem drag handle is pointer-only, so keyboard users
currently have no way to reorder tasks after the move actions were removed.
Update the TaskItem component to expose a keyboard-accessible reorder path on
the task row or drag handle by making it focusable and handling key events to
trigger the same reorder flow used by reorderTasks, or restore an equivalent
menu/shortcut action tied to the existing task actions. Use the TaskItem.vue
template and the reorderTasks/task action wiring as the main reference points
when adding the accessibility path.

In `@src/renderer/components/Task/TaskList.vue`:
- Around line 159-167: The drag cleanup in TaskList is incomplete:
`beforeUnmount` removes the pointer listeners but leaves
`document.body.classList` stuck with `task-dragging`, and there is no
`pointercancel` handling for interrupted drags. Update the drag lifecycle in the
TaskList component by ensuring the same cleanup used by `onDragUp` also runs
during unmount and on pointer cancellation, and wire a `pointercancel` listener
alongside `pointermove`/`pointerup` so the drag state is always cleared even
when the browser aborts the gesture.
- Around line 11-21: Restore a keyboard-accessible reorder path in TaskList and
TaskActions: the current drag-only flow via handle-down on task-item and the
non-focusable drag handle leaves keyboard and screen-reader users unable to move
tasks. Add an accessible reorder mechanism such as focusable move up/down
controls or equivalent keyboard handlers in TaskActions, and ensure TaskList
continues to support reordering through these controls alongside the existing
pointer drag behavior.
- Around line 254-322: The drag lifecycle in TaskList.vue leaves global drag
state behind if the component unmounts or the pointer is canceled, because the
cleanup in onDragUp() is not always reached. Update the drag cleanup path used
by onHandleDown(), onDragUp(), and beforeUnmount() so the same teardown runs in
every exit path: remove the pointermove/pointerup handlers, clear
draggingKeys/dropTargetKey/dropAfter, and always remove the "task-dragging" body
class. Also add pointercancel handling alongside pointerup so canceled drags
fully reset state.

In `@src/renderer/components/TaskDetail/TaskGeneral.vue`:
- Around line 256-265: The countdown timer in TaskGeneral.vue is started
unconditionally in mounted(), so non-scheduled tasks still get a per-second
update loop. Update the mounted()/beforeUnmount() flow to only create and clear
_nowTimer when the current task is scheduled (use isScheduled or the logic that
drives startingAfterText), and avoid setting nowMs for unscheduled tasks. This
should be implemented in the TaskGeneral component’s timer setup so the interval
only runs while needed.

In `@src/renderer/components/ui/date-time-picker/DateTimePicker.vue`:
- Around line 25-29: The DateTimePicker flow can commit a past timestamp when
“today” is selected because defaultTime() may initialize to an already-past 2:00
AM and the hourField/minuteField setters do not validate against Date.now().
Update the DateTimePicker.vue logic around defaultTime and the
hourField/minuteField commit path to prevent selecting a time-of-day earlier
than the current time for the chosen day, either by clamping to the next valid
time or blocking the commit with a clear state update. If a `startAt` is already
in the past at creation time, align this component’s behavior with the engine’s
expected handling and make that handling explicit in the selection/commit logic.

In `@src/renderer/store/task.ts`:
- Around line 820-849: The reorderTasks flow in task store is preserving a stale
optimistic order after api.reorderTasks fails, which causes
fetchList/applyTaskOrder to reapply and persist the wrong order. In
reorderTasks, clear the currentList entry in taskOrderMap before calling
fetchList() inside the catch block so the refetched data is not re-sorted by the
failed optimistic state; keep the existing success path unchanged and make sure
updateTaskOrder is only fed the confirmed order after a successful reorder.

---

Outside diff comments:
In @.github/workflows/release.yml:
- Around line 264-293: The Linux tagged-release asset naming in the release
workflow is using the wrong suffix, causing updater bundles to be published with
a .gz name. Update the extension handling in the bundle selection logic around
the asset creation in the release job so the basename check in the tag branch
matches the full .AppImage.tar.gz updater artifact, then keep copying the signed
asset and its .sig with the corrected asset name.

In `@scripts/build-updater-manifest.test.mjs`:
- Around line 1-45: Extend the coverage in buildManifest tests so every guard
clause is exercised, not just the missing-version path. Add assertions for the
missing-repo case in buildManifest, plus failures when a fragment is incomplete
(missing key, asset, or signature) and when the fragments directory is empty,
using the existing buildManifest helper and the temporary fragment setup in this
test file. Keep the current successful manifest assertions, but add focused
throws checks that reference buildManifest and the fragment JSON shape so
regressions in these validation paths are caught.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/release.yml:
- Line 241: The release workflow is referencing an undefined matrix property, so
the linker env var is always empty and triggers lint errors. Update the workflow
around the existing CARGO_TARGET_ARMV7_UNKNOWN_LINUX_GNUEABIHF_LINKER entry to
either remove the dead matrix.linker reference or add a real linker field to the
matrix/include definitions if armv7 support is intended. Make the same
correction anywhere else the same matrix.linker reference appears so the
workflow only uses defined matrix keys.

In `@src/shared/locales/ar/task.ts`:
- Around line 70-71: The new task locale entries in the ar task translation file
are still in English, so replace `start-now-fail`, `start-now-task-fail`, and
`reorder-task` with proper Arabic translations to match the rest of the locale
module. Also remove or retire the unused `move-task-up` and `move-task-down`
entries from the same task locale object since the related actions were removed,
and apply the same translation cleanup pattern in the other touched locale files
(for example the corresponding task locale definitions).

In `@src/shared/locales/de/task.ts`:
- Around line 71-72: The German locale entries in task.ts still contain English
placeholder text for start-now-fail, start-now-task-fail, and reorder-task.
Update the affected string values in the task translation object to proper
German equivalents, and make sure the same fix is applied to the related
reordered entry referenced by the comment. Use the existing locale key names to
locate and replace only the untranslated strings.
- Around line 71-72: Add the missing German scheduling entries in the task
locale object in task.ts so the scheduling UI no longer falls back to English.
Update the translation map alongside the existing task keys to include the
missing symbols such as scheduled, schedule-task, reschedule-task,
schedule-dialog-title, schedule-dialog-hint, schedule-pick-time,
schedule-confirm, schedule-start-at, schedule-start-at-placeholder,
starting-after, and the missed-schedule-* variants, keeping the naming and
interpolation style consistent with the existing task translations.

In `@src/shared/locales/el/task.ts`:
- Around line 72-73: The Greek locale entries still contain English strings for
the task-related keys. Update the translations in the el task locale object for
start-now-fail, start-now-task-fail, and reorder-task so they are fully
translated into Greek, keeping the existing placeholder symbol taskName intact.
Use the task.ts locale entries to locate and replace the untranslated values.
- Around line 72-73: The Greek locale in task.ts is missing the new scheduling
and missed-schedule translation keys, so add the same `scheduled`, `schedule-*`,
and `missed-schedule-*` entries that exist in the other locales. Update the
`el/task.ts` message map alongside the existing `start-now-*` keys, keeping the
key names consistent with the shared task locale structure so the Schedule and
Missed-Schedule dialogs can resolve Greek strings.

In `@src/shared/locales/es/task.ts`:
- Around line 72-73: The Spanish locale in task.ts still contains untranslated
English entries, so update the affected keys to proper Spanish. Edit the task
translation object and replace the values for start-now-fail,
start-now-task-fail, and reorder-task with Spanish text, keeping the existing
placeholders like {{taskName}} intact and ensuring the surrounding locale
entries remain consistent.
- Around line 72-73: The Spanish task locale is missing the full scheduling
block, so add the new scheduled-task strings to task.ts alongside the existing
start-now entries. Update the es locale object to include the scheduling-related
keys referenced by the UI, including scheduled, schedule-task, reschedule-task,
schedule-dialog-title, schedule-dialog-hint, schedule-pick-time,
schedule-confirm, schedule-start-at, schedule-start-at-placeholder,
starting-after, and the missed-schedule-* messages, keeping the translations
consistent with the existing Task locale structure.

In `@src/shared/locales/fa/task.ts`:
- Around line 70-71: The locale entries in task.ts still contain English strings
for the Persian bundle, specifically the keys start-now-fail,
start-now-task-fail, and reorder-task. Update these translations in the fa
locale object so they are fully localized to Persian while preserving any
placeholders such as {{taskName}}. Use the existing task translation keys in the
same export to locate and replace the untranslated values.
- Around line 70-71: The Persian task locale in task.ts is missing the
scheduling-related translation keys, so add the full scheduled, schedule-*, and
missed-schedule-* set there, including schedule-task-fail, alongside the
existing start-now entries. Use the existing task translation object structure
in src/shared/locales/fa/task.ts to insert the missing keys so the scheduling UI
resolves Persian strings instead of falling back to English.

In `@src/shared/locales/zh-CN/task.ts`:
- Around line 159-160: The newly added scheduling locale entries in task.ts
still contain English text, so translate the affected keys to Chinese to match
the rest of this locale file. Update the string values for start-now-fail,
start-now-task-fail, schedule-task-fail, and reorder-task in the zh-CN task
dictionary, keeping the existing placeholders like {{taskName}} intact.

In `@src/shared/locales/zh-TW/task.ts`:
- Around line 159-160: The zh-TW task locale still has untranslated scheduling
keys mixed in with translated content. Update the string values for
schedule-task-fail, start-now-fail, start-now-task-fail, and reorder-task in the
task locale object so they are in Traditional Chinese, matching the surrounding
entries. Use the existing locale keys in task.ts to locate and replace the
English placeholders without changing the key names or interpolation tokens like
"{{taskName}}".

---

Outside diff comments:
In `@src/renderer/components/Native/EngineClient.vue`:
- Around line 1048-1057: The startup missed-schedule scan in
checkMissedSchedules() only reads the first page from fetchScheduledTaskList(),
so tasks beyond the default TASK_LIST_FETCH_SIZE can be missed. Update the logic
to page through all scheduled tasks before filtering for scheduleMissed, using
the existing api.fetchScheduledTaskList flow and keeping the
useAppStore().showMissedScheduled call on the full accumulated result.

In `@src/renderer/components/Task/Index.vue`:
- Around line 676-686: `handleStartTaskNow` is handling errors differently from
the sibling task actions and can leak raw engine/Tauri messages to users. Update
the `useTaskStore().startNow(task.gid).catch(...)` block in `Index.vue` to match
`handleResumeTask`/`handlePauseTask` by checking `err.code === 1` and otherwise
always falling back to the translated `task.start-now-task-fail` message using
`taskName`. Keep the error handling pattern consistent with the other handlers
and avoid using `(err as Error)?.message` as the primary user-facing message.

In `@src/renderer/components/Task/ScheduleDialog.vue`:
- Around line 106-111: The ScheduleDialog.vue error path already falls back to
task.schedule-task-fail via this.$t in the catch block, but that key is missing
from some locale bundles. Add the task.schedule-task-fail translation to the ru,
th, and tr locale files so useTaskStore().setSchedule failures show a localized
message consistently across all supported languages.

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/shared/locales/tr/task.ts">

<violation number="1" location="src/shared/locales/tr/task.ts:71">
P2: Turkish users will see English text for the new scheduled-start and reorder strings. Translate these three values to Turkish to match the rest of the locale file.</violation>
</file>

<file name="src/shared/locales/ru/task.ts">

<violation number="1" location="src/shared/locales/ru/task.ts:72">
P2: New locale keys for scheduled start ('start-now-fail', 'start-now-task-fail') and drag reorder ('reorder-task') are in English instead of Russian. Russian UI users will see untranslated text for these features. Translate the values to match the rest of the file.</violation>
</file>

<file name="src/shared/locales/ar/task.ts">

<violation number="1" location="src/shared/locales/ar/task.ts:70">
P2: These three new translation keys have English values in the Arabic locale file. Arabic-speaking users will see untranslated English text for these messages.</violation>
</file>

<file name="src/shared/locales/hu/task.ts">

<violation number="1" location="src/shared/locales/hu/task.ts:70">
P3: These three new locale strings are in English but should be in Hungarian to match the rest of the hu locale file. Consider translating: "start-now-fail" (e.g., "A feladat indítása sikertelen"), "start-now-task-fail" (e.g., 'A(z) "{{taskName}}" feladat indítása sikertelen'), and "reorder-task" (e.g., "Feladat átrendezése. Mozgatás a Fel/Le billentyűkkel").</violation>
</file>

<file name="src/shared/locales/pt-BR/task.ts">

<violation number="1" location="src/shared/locales/pt-BR/task.ts:72">
P3: These three new pt-BR locale keys have English values instead of Portuguese translations. All other keys in this file are properly translated.</violation>

<violation number="2" location="src/shared/locales/pt-BR/task.ts:88">
P3: These three new pt-BR locale keys have English values instead of Portuguese translations.</violation>
</file>

<file name="src/shared/locales/ro/task.ts">

<violation number="1" location="src/shared/locales/ro/task.ts:71">
P1: The new locale strings "start-now-fail", "start-now-task-fail", and "reorder-task" use English text instead of Romanian translations. This breaks the locale contract and will display English text to Romanian users.</violation>

<violation number="2" location="src/shared/locales/ro/task.ts:87">
P2: Same issue — "reorder-task" uses English text instead of Romanian.</violation>
</file>

<file name="src/shared/locales/fr/task.ts">

<violation number="1" location="src/shared/locales/fr/task.ts:71">
P3: Localization gap: this is the French locale file but the translation is left as English. Add a French translation, e.g. "Échec du démarrage de la tâche planifiée".</violation>

<violation number="2" location="src/shared/locales/fr/task.ts:86">
P3: Localization gap: this French locale entry is still in English. Add a French translation, e.g. "Réorganiser la tâche. Appuyez sur Haut ou Bas pour déplacer".</violation>
</file>

<file name="src/shared/locales/zh-CN/task.ts">

<violation number="1" location="src/shared/locales/zh-CN/task.ts:9">
P2: New localization value is in English in the zh-CN locale file. Users will see English text instead of Chinese.</violation>

<violation number="2" location="src/shared/locales/zh-CN/task.ts:159">
P2: New localization values are in English in the zh-CN locale file. Users will see English text instead of Chinese.</violation>

<violation number="3" location="src/shared/locales/zh-CN/task.ts:171">
P2: New localization value is in English in the zh-CN locale file. Users will see English text instead of Chinese.</violation>
</file>

<file name="src/renderer/store/task.ts">

<violation number="1" location="src/renderer/store/task.ts:850">
P2: Drag reorder failures can now surface as unhandled promise rejections in UI event handlers. This comes from rethrowing in `reorderTasks` after local rollback/fetch, while current callers do not catch the rejection; keeping the error handled locally (or adding caller catches) avoids noisy runtime errors.</violation>
</file>

<file name="src/shared/locales/ca/task.ts">

<violation number="1" location="src/shared/locales/ca/task.ts:73">
P2: These three new localization values are in English but the file is the Catalan locale (ca). All surrounding entries are translated to Catalan. Translate these to match the locale.</violation>

<violation number="2" location="src/shared/locales/ca/task.ts:90">
P3: Same issue - English string in Catalan locale.</violation>
</file>

<file name="src/shared/locales/vi/task.ts">

<violation number="1" location="src/shared/locales/vi/task.ts:70">
P3: New locale keys are in English rather than Vietnamese. The surrounding error messages (pause-task-fail, resume-task-fail, move-task-up, move-task-down) all have proper Vietnamese translations. Consider translating these to match the rest of the file so users see consistent Vietnamese text.</violation>
</file>

<file name="src/shared/locales/el/task.ts">

<violation number="1" location="src/shared/locales/el/task.ts:72">
P2: These three new translation keys have English values instead of Greek translations. The rest of the file is fully translated — users will see English text for scheduled-task failures and reorder instructions. Please replace with Greek translations to match the rest of the locale.</violation>
</file>

<file name="src/shared/locales/es/task.ts">

<violation number="1" location="src/shared/locales/es/task.ts:72">
P2: Spanish locale entry is in English instead of Spanish. Translate to follow existing error message patterns (e.g., 'Hubo un fallo al' for fail messages, 'programada' for scheduled).</violation>

<violation number="2" location="src/shared/locales/es/task.ts:88">
P2: Spanish locale entry is in English instead of Spanish. Translate to follow existing key conventions.</violation>
</file>

<file name="src/shared/locales/ja/task.ts">

<violation number="1" location="src/shared/locales/ja/task.ts:72">
P3: The three newly added string keys "start-now-fail", "start-now-task-fail", and "reorder-task" use English values in the Japanese locale file. Japanese users will see English text for these messages. Add Japanese translations for each.</violation>
</file>

<file name="src/shared/locales/bg/task.ts">

<violation number="1" location="src/shared/locales/bg/task.ts:71">
P2: Missing Bulgarian translation for `"start-now-fail"`. The value is in English, but this is the Bulgarian locale file. Follow the pattern from similar error keys like `"pause-task-fail"` (грешка при спиране) and `"resume-task-fail"` (грешка при възобновяване) for consistency.</violation>

<violation number="2" location="src/shared/locales/bg/task.ts:72">
P2: Missing Bulgarian translation for `"start-now-task-fail"`. Follow the established Bulgarian pattern from `"pause-task-fail"` (грешка при спиране на задачата) and `"resume-task-fail"` (грешка при възобновяване на задачата).</violation>

<violation number="3" location="src/shared/locales/bg/task.ts:87">
P2: Missing Bulgarian translation for `"reorder-task"`. Nearby accessibility keys like `"move-task-up"` (Преместване на задача нагоре) and `"move-task-down"` (Преместване на задача надолу) show the expected locale pattern.</violation>
</file>

<file name="src/shared/locales/ko/task.ts">

<violation number="1" location="src/shared/locales/ko/task.ts:70">
P2: Korean locale entries for start-now-fail, start-now-task-fail, and reorder-task contain English text. The surrounding keys are translated to Korean — these should be translated for consistency so Korean users see localized error and accessibility messages.</violation>
</file>

<file name="src/shared/locales/nb/task.ts">

<violation number="1" location="src/shared/locales/nb/task.ts:70">
P2: These three new locale entries are in English instead of Norwegian Bokmål. They will display as English prompts in the Norwegian UI. Translate them for consistency with the rest of the file.</violation>

<violation number="2" location="src/shared/locales/nb/task.ts:86">
P2: Same untranslated issue — "Reorder task. Press Up or Down to move" shows English text in the Norwegian locale. Translate to Norwegian.</violation>
</file>

<file name="src/renderer/components/Task/TaskItem.vue">

<violation number="1" location="src/renderer/components/Task/TaskItem.vue:17">
P2: When the drag handle has focus, all key presses are swallowed, so list-level shortcuts stop working from that state. Using `.stop` only for handled keys (or removing it here) preserves global shortcuts while keeping ArrowUp/ArrowDown reorder behavior.</violation>
</file>

<file name="src/renderer/components/ui/date-time-picker/DateTimePicker.vue">

<violation number="1" location="src/renderer/components/ui/date-time-picker/DateTimePicker.vue:26">
P2: The new future clamp can still allow near-immediate scheduling because rounding seconds to `00` moves the minimum backward within the minute. Computing the minimum as a minute-ceil timestamp after adding 60s would keep the guard consistently at least one minute ahead.</violation>
</file>

<file name="src/shared/locales/zh-TW/task.ts">

<violation number="1" location="src/shared/locales/zh-TW/task.ts:9">
P3: Add Traditional Chinese translation for the new `schedule-task-fail` locale key. Users will see English text instead of Chinese in the UI.</violation>

<violation number="2" location="src/shared/locales/zh-TW/task.ts:159">
P3: Add Traditional Chinese translation for `start-now-fail`. The English fallback will be shown to zh-TW users.</violation>

<violation number="3" location="src/shared/locales/zh-TW/task.ts:160">
P3: Add Traditional Chinese translation for `start-now-task-fail`. This error message will appear in Chinese UI context but remains in English.</violation>

<violation number="4" location="src/shared/locales/zh-TW/task.ts:171">
P3: Add Traditional Chinese translation for the `reorder-task` accessibility hint. This is shown as an aria label for drag-reorder interactions.</violation>
</file>

<file name="src/renderer/components/Task/MissedScheduleDialog.vue">

<violation number="1" location="src/renderer/components/Task/MissedScheduleDialog.vue:120">
P2: Bulk start now fires every `startNow` in parallel, which multiplies `fetchList`/`saveSession` side effects and can cause avoidable request bursts and state thrash for larger missed lists. Keeping failure tracking but processing sequentially avoids the concurrency spike while preserving the new partial-failure behavior.</violation>
</file>

<file name="src/renderer/components/Task/TaskList.vue">

<violation number="1" location="src/renderer/components/Task/TaskList.vue:336">
P2: When a user tabs to a non-selected task's drag handle and presses ArrowUp/Down while other tasks are selected, `moveSelection` moves the unrelated selected tasks instead of the focused task. The `fallbackKey` path only activates when no items are selected (`moving.length === 0`), so a non-selected focused task is ignored when the selection has other items. Consider checking whether the fallback task is in the selection before falling back to the full selection, so that the keyboard interaction targets the task the user is actually focused on.</violation>

<violation number="2" location="src/renderer/components/Task/TaskList.vue:343">
P2: `moveSelection` calls `reorderTasks` without `await` or `.catch()`, producing an unhandled promise rejection on failure. The store's `reorderTasks` now re-throws errors after rollback (`throw err`), so any backend save failure triggers an unhandled rejection even though the local state was already restored via `fetchList`. Add `.catch(() => {})` to suppress the rejection (the rollback already ran) or `await` the call if the caller should handle it.</violation>
</file>

<file name="src/shared/locales/en-US/task.ts">

<violation number="1" location="src/shared/locales/en-US/task.ts:9">
P3: `schedule-task-fail` is added to only en-US, zh-CN, and zh-TW, while the other three new keys (`start-now-fail`, `start-now-task-fail`, `reorder-task`) are added to all 26 locale files. Since i18next's `fallbackLng: "en-US"` covers the missing locales at runtime, this won't cause a visible issue. Still, for consistency with how the rest of this PR handles new keys, consider adding `schedule-task-fail` with English placeholder text to the remaining 23 locale files as well.</violation>

<violation number="2" location="src/shared/locales/en-US/task.ts:9">
P3: This Simplified Chinese locale adds new scheduling/reorder strings in English, which creates inconsistent mixed-language UI in those states. Localizing the newly added keys would align this file with the rest of the translated entries.</violation>
</file>